Systems and Methods for Efficient Data Storage

ABSTRACT

Various embodiments of the present invention provide systems and methods for preparing and accessing super sector data sets. As an example, a data storage system including a storage medium is disclosed. The storage medium includes a first servo data region and a second servo data region separated by a user data region. The user data region includes at least a portion of a first codeword and a portion of a second codeword that are together associated with a common header data.

CROSS REFERENCE TO RELATED APPLICATIONS

The Present application is a continuation of U.S. patent application Ser. No. 12/750,654 entitled “Systems and Methods for Efficient Data Storage” and filed by Jin et al. on Mar. 30, 2010. The entirety of the aforementioned reference is incorporated herein by reference for all purposes.

BACKGROUND OF THE INVENTION

The present inventions are related to storing data, and more particularly to formats, systems and methods for storing data to a storage medium.

A read channel integrated circuit is a component of a magnetic storage device. In operation, a read channel component converts and encodes data to enable a read/write head assembly to write data to a disk and to subsequently read data back. In, for example, a hard disk drive, the disk typically includes many tracks containing encoded data that extend around the disk in a radial pattern. Each track includes one or more user data regions as well as intervening servo data regions. The information of the servo data regions is used to position the read/write head assembly in relation to the disks so that the information stored in the user data regions may be retrieved accurately.

FIG. 1 shows a storage medium 100 with two exemplary tracks 150, 155 indicated as dashed lines. The tracks are segregated by servo data written within wedges 160, 165. These wedges include data and supporting bit patterns 110 that are used for control and synchronization of the read/write head assembly over a desired location on storage medium 100. In particular, these wedges generally include a preamble pattern 152 followed by a sector address mark 154 (SAM). Sector address mark 154 is followed by a Gray code 156, and Gray code 156 is followed by burst information 158. It should be noted that while two tracks and two wedges are shown, hundreds of each would typically be included on a given storage medium. Further, it should be noted that a servo data set may have two or more fields of burst information. Between the bit patterns 110, a user data region 184 is provided. Such user data regions 184 include substantial overhead and wasted areas resulting in a reduction in the density of data maintained in the user data region 184.

Hence, for at least the aforementioned reasons, there exists a need in the art for advanced systems and methods for maintaining data on a storage medium.

BRIEF SUMMARY OF THE INVENTION

The present inventions are related to storing data, and more particularly to formats, systems and methods for storing data to a storage medium.

Various embodiments of the present invention provide data storage systems that include a storage medium. The storage medium includes a first servo data region and a second servo data region separated by a user data region. The user data region includes at least a portion of a first codeword and a portion of a second codeword that are together associated with a common header data. In some instances, the first codeword and the second codeword are low density parity check encoded codewords. In various instances of the aforementioned embodiments, the portion of the first codeword is all of the first codeword, and the portion of the second codeword is less than all of the second codeword. In such a case, the remaining part of the second codeword is included in another user data region.

In some cases, the data storage system further includes an encoder circuit operable to: receive write data; encode the write data into the first codeword and the second codeword; and combine the portion of the first codeword with the portion of the second codeword and the common header data to form a super sector data set. In some such cases, the encoder circuit includes a low density parity check encoder, and the first codeword and the second codeword are low density parity check encoded codewords. In one or more such cases, the encoder circuit further includes a user data region matching circuit that is operable to combine the portion of the first codeword with the portion of the second codeword and the common header data into the super sector data set. In particular cases, the super sector data set includes greater than two times the number of bit periods in the first codeword, and less than the number of bit periods of the user data region.

In one or more cases, the portion of a first codeword, the portion of a second codeword and the common header data are assembled in a super sector data set. The systems further include a decoder circuit operable to: receive the super sector data set; synchronize to the super sector data set using the common header data; divide the super sector data set to yield the portion of the first codeword and the portion of the second codeword; and decode the first codeword and the second codeword to yield the write data. In some such cases, the decoder circuit includes a low density parity check decoder, and the first codeword and the second codeword are low density parity check encoded codewords.

Other embodiments of the present invention provide data decoder circuits having a codeword boundary matching circuit and a data processing circuit. The codeword boundary matching circuit is operable to: receive a super sector data set having a first codeword, a second codeword and a common header data; and divide the super sector data set to yield the first codeword and the second codeword. The data processing circuit operable to: apply a decoding algorithm to the first codeword to yield a first data set, and apply the decoding algorithm to the second codeword to yield a second data set. In some cases, the first codeword and the second codeword are low density parity check encoded data, and the data processing circuit includes a low density parity check decoder circuit.

This summary provides only a general outline of some embodiments of the invention. Many other objects, features, advantages and other embodiments of the invention will become more fully apparent from the following detailed description, the appended claims and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the various embodiments of the present invention may be realized by reference to the figures which are described in remaining portions of the specification. In the figures, like reference numerals are used throughout several drawings to refer to similar components. In some instances, a sub-label consisting of a lower case letter is associated with a reference numeral to denote one of multiple similar components. When reference is made to a reference numeral without specification to an existing sub-label, it is intended to refer to all such multiple similar components.

FIG. 1 depicts an existing storage medium including servo data;

FIG. 2 depicts a storage device including a read channel capable of reading and writing a concatenated user data set in accordance with one or more embodiments of the present invention;

FIG. 3 a depicts a read channel circuit operable to read and write concatenated user data sets in accordance with various embodiments of the present invention;

FIG. 3 b depicts another read channel circuit operable to read and write concatenated user data sets in accordance with other embodiments of the present invention;

FIG. 4 a is a timing diagram depicting an exemplary write operation of the read channel of FIG. 3 in accordance with some embodiments of the present invention;

FIG. 4 b is a timing diagram depicting an exemplary read operation of the read channel of FIG. 3 in accordance with some embodiments of the present invention; and

FIG. 5 is a flow diagram showing a method for accessing a storage medium using a concatenated user data set in accordance with some embodiments of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present inventions are related to storing data, and more particularly to formats, systems and methods for storing data to a storage medium.

Various embodiments of the present invention provide improved format efficiency for user data maintained on a storage medium. Such embodiments provide for concatenating codewords into a super sector data set that is stored to a storage medium. As used herein, the phrase “super sector data set” is used in its broadest sense to mean a data set that includes more than one codeword assembled together with a common header data. Such concatenation, among other things, reduces the amount of overhead associated with maintaining data on a storage medium. Various instances of the aforementioned embodiments support split codewords allowing for utilization of orphan regions of a storage medium. In one particular instance of the aforementioned embodiments, a single preamble field and synchronization pattern is included in each user data region to synchronize to the data maintained in the user data region. As such, only a single preamble and synchronization pattern may be used to synchronize to multiple codewords within the user data region. The data received from the user data region is re-assembled into codewords for processing by a read channel circuit.

Turning to FIG. 2, a storage system 200 including a read channel 210 with support for concatenated user data is depicted in accordance with various embodiments of the present invention. Storage system 200 may be, for example, a hard disk drive. Read channel 210 may include support for concatenated user data (i.e., super data sets) consistent with that discussed below in relation to FIG. 3, and/or may operate consistent with one or more of FIGS. 4-5. Further, read channel 210 includes a data detector, such as, for example, a Viterbi algorithm data detector. In addition to read channel 210, storage system 200 includes a preamplifier 270 that amplifies a minute electrical signal received from a read/write head assembly 276. Read/write head assembly 276 is disposed in relation to a disk platter 278. Storage system 200 also includes an interface controller 220, a hard disk controller 266, a motor controller 268, and a spindle motor 272. Interface controller 220 controls addressing and timing of data to/from disk platter 278. The data on disk platter 278 consists of groups of magnetic signals that may be detected by read/write head assembly 276 when the assembly is properly positioned over disk platter 278. In one embodiment, disk platter 278 includes magnetic signals recorded in accordance with a perpendicular recording scheme. In other embodiments of the present invention, disk platter 278 includes magnetic signals recorded in accordance with a longitudinal recording scheme.

In a typical read operation, read/write head assembly 276 is accurately positioned by motor controller 268 over a desired data track on disk platter 278. Motor controller 268 both positions read/write head assembly 276 in relation to disk platter 278 and drives spindle motor 272 by moving read/write head assembly to the proper data track on disk platter 278 under the direction of hard disk controller 266. Spindle motor 272 spins disk platter 278 at a determined spin rate (RPMs). Once read/write head assembly 278 is positioned adjacent the proper data track, magnetic signals representing data on disk platter 278 are sensed by read/write head assembly 276 as disk platter 278 is rotated by spindle motor 272. The sensed magnetic signals are provided as a continuous, minute analog signal representative of the magnetic data on disk platter 278. This minute analog signal is transferred from read/write head assembly 276 to read channel 210 via preamplifier 270. Preamplifier 270 is operable to amplify the minute analog signals accessed from disk platter 278. In turn, read channel 210 decodes and digitizes the received analog signal to recreate the information originally written to disk platter 278. This data is provided as read data 203 to a receiving circuit. A write operation is substantially the opposite of the preceding read operation with write data 201 being provided to read channel module 210. This data is then encoded and written to disk platter 278.

Turning to FIG. 3 a, a read channel circuit 205 that is operable to read and write concatenated user data sets (i.e., super sector data sets) is shown in accordance with various embodiments of the present invention. Read channel circuit 205 includes an encoder circuit 233 and a decoder circuit 273. Encoder circuit 233 includes a data encoding circuit 213, an encoded data buffer 219, and a user data region matching circuit 223. Write data 201 is provided to data encoding circuit 213. Write data 201 may be received from any data source known in the art, and may be received either via a parallel data bus or via a serial data bus as are known in the art. In one particular embodiment of the present invention, write data 201 is received from an upstream processor (not shown). Write data 201 is assembled by data encoding circuit 213 into codewords that are provided to encoded data buffer 219. In one particular embodiment, data encoding circuit 213 is a low density parity check (LDPC) encoder circuit as are known in the art. In such embodiments, data encoding circuit 213 provides a series of LDPC codewords to encoded data buffer 219. Such LDPC codewords include portions of write data 201 along with various encoding information as are known in the art. As a particular example, the codewords may each be four thousand, ninety six user bits plus a number of encoding bits (e.g., parity bits). In some cases, the number of encoding bits may be between forty and four hundred depending upon the robustness of the encoding that is performed.

Encoded data buffer 219 may be any data storage device capable of storing the produced codewords from data encoding circuit 213 until the codewords can be processed and written to a storage medium. As an example, encoded data buffer 219 may be a first in, first out memory that provides portions of stored codewords via a codeword interface 227 to user data region matching circuit 223 upon assertion of a request signal 228.

User data region matching circuit 223 is operable to assemble two or more codewords into a super sector data set that is provided as an encoded data output 293 to a storage medium. Encoded data output 293 is provided after write gate signal 287 has been asserted sufficient time for a header data 388 to be written to the storage medium. A header data insertion circuit 241 provides header data 288 one bit at a time during a header period that directly precedes the writing of encoded data output 293 to the storage medium. Header data 288 may be any header data known in the art. Providing header data 288 directly preceding encoded data output 293 is controlled based upon assertion of write gate 293. Header data 288 becomes part of the super sector data set written to the storage medium. In one particular embodiment of the present invention, header data 288 includes a preamble and synchronization field that may be used to identify the beginning of the user data and to synchronize to the super sector data set upon read back from the storage medium. Based upon the disclosure provided herein, one of ordinary skill in the art will recognize a variety of header data that may be used in relation to different embodiments of the present invention.

The number of codewords and portions of codewords assembled into the super sector data set may be matched to the size of the user data region of the storage medium. The following equation represents the amount of data incorporated in the super sector data set:

${{Number}\mspace{14mu} {of}\mspace{14mu} {Codewords}} = {\frac{{{Size}\mspace{14mu} {of}\mspace{14mu} {User}\mspace{14mu} {Data}\mspace{14mu} {Region}} - {{Size}\mspace{14mu} {of}\mspace{14mu} {Header}\mspace{14mu} {Data}}}{{Size}\mspace{14mu} {of}\mspace{14mu} {Codewords}}.}$

As an example, where the super sector data set ended on a codeword boundary for the last user data region, the size of the user data region is ten thousand, seven hundred fifty bits, the size of the header data is one hundred bits, and the size of the codewords is four thousand, ninety six bits, the number of codewords calculated by the preceding equation is 2.6. In this case, the succeeding super sector data set starts with the header data followed by the next two complete codewords available from encoded data buffer 219, and a portion of the next codeword from encoded data buffer 219 equivalent to 0.6 of the codeword. The remaining portion (i.e., the last 0.4 codeword) of the partial codeword is written after the header data in the succeeding super sector data set.

User data region matching circuit 223 receives a servo gate signal 251 from a servo data processing circuit (not shown) that indicates the location of a user data region relative to intervening servo data regions. Once the super sector data set is assembled as discussed above and servo gate signal 251 indicates the beginning of the user data region, user data region matching circuit 223 asserts a write gate signal 287 and serially provides the assembled super sector data set one bit at a time via encoded data output 293. This information is provided to a write circuit (not shown) that is responsible for writing the data to the incorporated storage medium.

Decoder circuit 273 includes a header synchronization circuit 252, a codeword boundary matching circuit 253, a decoded data buffer 256, and a data processing circuit 263. Header synchronization circuit 252 receives a read data input 296 derived from the storage medium, and synchronizes to the frequency and phase of the received data stream using the preamble and synchronization information included in the header data associated with the received data. This attempt to synchronize begins when servo gate signal 251 indicates that the servo data region has ended and the user data region has begun. Upon synchronizing to the received data stream, header synchronization circuit 252 asserts a sync found signal 254 indicating that the data received via read data input 296 is valid user data. Header synchronization circuit 252 may be any circuit known in the art that is capable of synchronizing to a data set derived from a user data region of a storage medium, and asserting a data available indicator signal.

Codeword boundary matching circuit 253 receives read gate input 254 and read data input 296, and based thereon assembles the received data into full codewords. Thus, for example, where the end of a user data region includes the first portion of a codeword, codeword boundary matching circuit 253 waits to receive the second portion of the codeword from the beginning of the succeeding user data region before providing the completed codeword. Codeword boundary matching circuit 253 uses the information provided via indicator 297 from codeword concatenation table circuit 283 to identify the location of codewords within the data provided via read data input 296. In some implementations, one or more counters synchronized to sync found signal 254 are used to count bits of codewords and codeword portions derived from a given user data region.

Codeword boundary matching circuit 253 provides codewords or portions of codewords to decoded data buffer 256, along with a codeword boundary signal 258 indicating a separation between codewords and a data valid signal 257 that is used to indicate that data on any given clock cycle is valid. The combination of these signals are used to write assembled codewords in decoded data buffer 256. Based upon the disclosure provided herein, one of ordinary skill in the art will recognize other interfaces that may be used to transfer data from codeword boundary matching circuit 253. Decoded data buffer 256 may be any data storage device capable of storing the codewords from codeword boundary matching circuit 253 until the codewords can be processed by data processing circuit 263. As an example, decoded data buffer 256 may be a first in, first out memory that provides codewords from codeword boundary matching circuit 253 to data processing circuit 263. Data processing circuit 263 processes the received data and provides read data 203. Where no processing errors are incurred, read data 203 corresponds to the information originally received as write data 201.

Data processing circuit 263 may be any circuit known in the art operable to process encoded data derived from a storage medium in an attempt to recover the original data set that was encoded and written to the storage medium. As an example, data processing circuit 263 may be implemented including a decoder circuit as are known in the art that is operable to reverse the encoding applied by data encoding circuit 213. Such a data decoder circuit may be, but is not limited to an LDPC decoder circuit. Based upon the disclosure provided herein, one of ordinary skill in the art will recognize a myriad of data processing circuits that may be used in relation to different embodiments of the present invention.

Turning to FIG. 3 b, a read channel circuit 306 that is operable to read and write concatenated user data sets (i.e., super sector data sets) is shown in accordance with various embodiments of the present invention. Read channel circuit 306 includes an encoder circuit 334 and a decoder circuit 374. Encoder circuit 334 includes a user data matching circuit 324, a data encoding circuit 314, and a data write circuit 304. Write data 301 is provided to user data region matching circuit 324. Write data 301 may be received from any data source known in the art, and may be received either via a parallel data bus or via a serial data bus as are known in the art. In one particular embodiment of the present invention, write data 301 is received from an upstream processor (not shown). Write data 301 is assembled by user data region matching circuit 324 to include enough data to fill an entire user data region on a storage medium. The amount of user data assembled is approximately equal to the size of the user data region less the number of encoding bits that are applied to the data and the amount of header data that will precede the data on the storage medium. Further, in some cases, the assembled data is interleaved (i.e., shuffled) by user data matching circuit 324 to reduce the impact of any localized noise on the later recovered data set. The assembled and interleaved user data is provided to a data encoding circuit 314 that performs a data encoding on the received user data. The data encoding may be, for example, LDPC encoding as is known in the art. Data encoding circuit 314 provides the encoded data as a super sector data set to a data write circuit 304. Data write circuit 304 receives servo gate 251 from a servo data processing circuit (not shown) that indicates the location of a user data region relative to intervening servo data regions. Once the servo gate 251 is asserted, data write circuit 304 asserts write gate signal 387.

Based upon the assertion of write gate signal 387, a header data insertion circuit 341 begins spooling out header data 388 that will become part of the super sector data set on the storage medium. Once the header data is complete, data write circuit 304 begins writing the encoded data out as encoded data output 394 to the storage medium. Header data 388 and encoded data output 394 is provided to a downstream write circuit (not shown) that is responsible for writing the data to the incorporated storage medium.

Decoder circuit 374 includes a header synchronization circuit 352, a detect/decode circuit 353, and a user data separating circuit 356. Header synchronization circuit 353 receives a read data input 396 derived from the storage medium, and synchronizes to the frequency and phase of the received data stream using the preamble and synchronization information included in the header data associated with the received data. This attempt to synchronize begins when servo gate signal 251 indicates that the servo data region has ended and the user data region has begun. Upon synchronizing to the received data stream, header synchronization circuit 352 asserts a sync found signal 354 indicating that the data received via read data input 396 is valid user data. Header synchronization circuit 352 may be any circuit known in the art that is capable of synchronizing to a data set derived from a user data region of a storage medium, and asserting a data available indicator signal.

Data processing circuit 353 may be any circuit known in the art operable to process encoded data derived from a storage medium in an attempt to recover the original data set that was encoded and written to the storage medium. As an example, data processing circuit 353 may be implemented including a data detector circuit and a data decoder circuit as are known in the art. Such a data detector circuit may be, but is not limited to, a Viterbi algorithm detector circuit. The decoder circuit may be, but is not limited to an LDPC decoder circuit. Based upon the disclosure provided herein, one of ordinary skill in the art will recognize a myriad of data processing circuits that may be used in relation to different embodiments of the present invention. As an example, data processing circuit 353 may be one of the data processing circuits disclosed in U.S. patent application Ser. No. 12/114,462 entitled “Systems and Methods for Queue Based Data Detection and Decoding”, and filed May 8, 2008 by Yang et al. The entirety of the aforementioned reference is incorporated herein by reference for all purposes. As another example, data processing circuit 263 may be one of the data processing circuits disclosed in U.S. patent application Ser. No. 12/430,927 entitled “Systems and Methods for Hard Decision Assisted Decoding”, and filed Apr. 28, 2009 by Zhong et al. The entirety of the aforementioned reference is incorporated herein by reference for all purposes. As yet another example, data processing circuit 263 may be one of the data processing circuits disclosed in U.S. patent application Ser. No. 11/341,963 entitled “Systems and Methods for Error Reduction Associated with Information Transfer”, and filed Jan. 26, 2006 by Song et al. The entirety of the aforementioned reference is incorporated herein by reference for all purposes.

Data processing circuit 353 provides a decoded data set to a user data separation circuit 356. User data separation circuit 356 is operable to receive the decoded data and to perform any de-interleaving that may be required to assemble the data in the form originally provided as write data 301. In some cases, such interleaving is applied by data encoding circuit 314 to limit the effects of any localized noise in the data by interleaving or mixing up the user data. The de-interleaved data is then provided by user data separating circuit 356 as read data 303.

Turning to FIG. 4 a, a timing diagram 400 depicts an exemplary write operation of read channel circuit 205 of FIG. 3 in accordance with some embodiments of the present invention. As shown, encoded data output 293 is a series of data bits corresponding to different regions to be written to a storage medium. In particular, encoded data output 293 is null for a period corresponding to a servo data region 403 that is placed on the storage medium as a reference for where a read/write head assembly exists in relation to the storage medium. During the servo data region 403, servo gate signal 251 is asserted at a level 425 indicating to user data region matching circuit 223 that no data can be written to the storage medium. Once the servo data region 403 completes, servo gate signal 251 de-asserts.

Upon de-assertion of servo gate signal 251, user data region matching circuit 223 asserts write gate signal 287 at a level 437 while at the same time providing a series of data bits corresponding to user data region 405. In particular, user data region matching circuit 223 provides bits corresponding to a header 415. Header 415 may be used to synchronize to the data written in user data region 405. This header may include, for example, a preamble followed by a synchronization pattern as is known in the art. Once user data region matching circuit 223 completes writing header 415, user data region matching circuit 223 writes the next codeword data available from encoded data buffer 219. Where, for example, the user data preceding servo data 403 ended on a codeword boundary, user data region matching circuit 223 begins writing the next codeword. Alternatively, where the user data preceding servo data 403 ended midway through a codeword, user data region matching circuit 223 begins writing at the midway point of the same codeword. Once the current codeword (i.e., codeword A) completes, user data region matching circuit 223 accesses the next code word (i.e., codeword B) from encoded data buffer 219 and provides it in serial as encoded data output 293. Once this codeword (i.e., codeword B) completes, user data region matching circuit 223 begins accessing the next code word (i.e., codeword C) from encoded data buffer 219 and provides a portion of the codeword as encoded data output 293. Some time before the end of user data region 405, user data region matching circuit 223 cuts off the writing of the codeword and subsequently writes a post-amble pattern 491. Such a post-amble pattern indicates the end of the codewords that were written to user data region 405. Once post-amble pattern 491 is written, user data region matching circuit 223 de-asserts write gate signal 287.

After the end of user data region 405, servo gate signal 251 is again asserted corresponding to a servo data region 407 that is placed on the storage medium as a reference for where a read/write head assembly exists in relation to the storage medium. Assertion of servo gate signal 251 at a level 427 indicates to user data region matching circuit 223 that no data can be written to the storage medium. Once the servo data region 407 completes, servo gate signal 251 de-asserts.

Upon de-assertion of servo gate signal 251, user data region matching circuit 223 asserts write gate signal 287 at a level 439 while at the same time providing a series of data bits corresponding to a user data region 409. In particular, user data region matching circuit 223 provides bits corresponding to a header 417. Header 417 may be used to synchronize to the data written in user data region 409. This header may include, for example, a preamble followed by a synchronization pattern as is known in the art. Once user data region matching circuit 223 completes writing header 417, user data region matching circuit 223 writes the remaining portion of codeword C accessed from encoded data buffer 219 as encoded data output 293. User data region matching circuit 223 continues writing this codeword until it completes. Once complete, user data region matching circuit 223 accesses the next codeword (i.e., codeword D) from encoded data buffer 219 and provides it as encoded data output 293 to be written to the storage medium. This process continues until near the end of user data region 409 where another post-amble pattern is written and user data region 409 completes. Of note, such an approach assembles one or more codewords into a super sector data set that is written to a user data region of the storage medium. Of note, use of a common header to synchronize to the super sector data set increases usable bit density of the user data regions.

Turning to FIG. 4 b, a timing diagram 401 depicts an exemplary read operation of read channel circuit 205 of FIG. 3 in accordance with some embodiments of the present invention. As shown, read data input 296 is the same series of data bits written to the storage medium in the example of FIG. 4 a. In particular, read input 296 includes servo data 403 read from the storage medium and used to determine the location of a read/write head assembly relative to the storage medium. During the servo data region 403, servo gate signal 251 is asserted at level 425 indicating to header synchronization circuit 252 that a header from user data region 405 is soon to follow. As servo gate signal 251 de-asserts, header synchronization circuit 252 begins the process of identifying a preamble pattern and synchronization pattern of header 415. Once header 415 is identified, header synchronization circuit 252 asserts sync found signal 254 at a level 457.

Once the bits associated with header 415 have been received, codeword boundary matching circuit 253 asserts data valid signal 257. With data valid signal 257 asserted, the data bits provided as codeword output 259 are stored to decoded data buffer 256. Codeword boundary matching circuit 253 maintains a count of the number of codeword bits that have been received. This count is continued until the number of remaining bits have been received in accordance with the following equation:

Number of Remaining Bits=Number of Bits in a Codeword−Number of Received Codeword Bits.

For example, where the total number of bits per codeword is four thousand, ninety six bits, and one thousand of the bits were received from a preceding user data region, the number of remaining bits is three thousand, ninety six bits. Alternatively, where the preceding user data region ended on a codeword boundary, the number of received codeword bits is zero, and the number of remaining bits is four thousand, ninety six bits. Once the number of remaining bits of codeword A have been received, codeword boundary matching circuit 253 asserts codeword boundary signal 258 (indicated as 463) indicating the end of codeword A, and the beginning of the next codeword (i.e., codeword B). Codeword B is then provided as codeword output 259 to decoded data buffer 256. This continues until the number of remaining bits of codeword B are received at which time codeword boundary signal 258 (indicated as 465) is asserted indicating the end of the codeword, and the beginning of the next codeword (i.e., codeword C). Codeword C is then provided as codeword output 259 to decoded data buffer 256 until post-amble 491 is identified and data valid signal 257 is de-asserted by codeword boundary matching circuit 253. At this juncture, the number of received codeword bits (the number of bits in codeword C first part) is less than the number of bits in a codeword. Thus, the count will be maintained and continued in the succeeding user data region 409.

Read input 296 includes servo data 407 read from the storage medium and used to determine the location of a read/write head assembly relative to the storage medium. During the servo data region 407, servo gate signal 251 is asserted at level 427 indicating to header synchronization circuit 252 that a header from user data region 409 is soon to follow. As servo gate signal 251 de-asserts, header synchronization circuit 252 begins the process of identifying a preamble pattern and synchronization pattern of header 417. Once header 417 is identified, header synchronization circuit 252 asserts sync found signal 254 at a level 459.

Once the bits associated with header 417 have been received, codeword boundary matching circuit 253 asserts data valid signal 257. With data valid signal 257 asserted, the data bits provided as codeword output 259 are stored to decoded data buffer 256. Codeword boundary matching circuit 253 counts the remaining portion of codeword C (i.e., codeword C second part) at which point codeword boundary matching circuit 253 asserts codeword boundary signal 258 (indicated as 467) indicating the end of codeword C, and the beginning of the next codeword (i.e., codeword D). This process continues until the desired read data is obtained from the storage medium.

Turning to FIG. 5, a flow diagram 500 showing a method for accessing a storage medium using a concatenated user data set in accordance with some embodiments of the present invention. Following flow diagram 500, it is determined whether a read request is received (block 505) or whether a write request is received (block 510). A requesting device or system may be, but is not limited to, a processor. A read request may include an address and/or data range on the storage medium from which data is to be read by a requesting device or system. A write request may indicate an address and include a data set that is to be written to the storage medium. Based upon the disclosure provided herein, one of ordinary skill in the art will recognize a variety of requesting devices or systems that may be used in relation to different embodiments of the present invention, and/or a variety of address and/or data ranges that may be used to identify locations on the storage medium where data is to be read or written.

Where a read request is received (block 505), one or more sectors on the storage medium where the requested data is stored are accessed (block 515), and the corresponding data is retrieved from the sector(s) (block 520). The access and retrieve processes may be any access and retrieve process known in the art. The received data includes super sector data set(s) that are received and divided into individual codewords (block 525). Such division into individual codewords includes synchronizing using a header data and counting the bits received after the end of the header data. A counter is maintained that counts up to the number of bits per codeword. Where a codeword is spread across a sector boundary, the counter continues until the end of the user data region and continues once bits corresponding to the codeword begin being received in the subsequent user data region. As the counter reaches the number of bits per codeword, an indication of a separation between the codewords is asserted, and the next codeword begins to be assembled from the received data. This process continues until all of the codewords from the retrieved data are separated into individual codewords.

The individual codewords are provided to a data processing circuit where the codewords are decoded to recover the data originally encoded to make the codewords (block 530). This processing may include, but is not limited to, one or more iterations through a data detector circuit and a data decoder circuit as is known in the art. In one particular case, the aforementioned data detector circuit is a Viterbi algorithm data detector circuit and the data decoder circuit is an LDPC decoder circuit. Based upon the disclosure provided herein, one of ordinary skill in the art will recognize various data processing circuits that may be used in relation to different embodiments of the present invention. The decoded codewords are then provided to the requesting device or system (block 535).

Alternatively, where a write request is received (block 510), it is determined whether the write request is previously written data (i.e., data from the storage medium that has been read and modified) (block 540). Where the data was not previously written (block 540), a new sector to receive the write data (i.e., an unused sector) is selected (block 575). The write data is encoded into individual codewords (block 580). For example, where a codeword is four thousand, ninety six bits including sixty added encoding bits, four thousand, thirty bits of the write data are encoded to a yield four thousand, ninety six bit codeword. In some embodiments of the present invention, the applied encoding is an LDPC encoding and the added encoding bits are parity bits that are calculated and incorporated in the codeword as is known in the art.

Header data is prepared (block 585). This header data may include a preamble pattern and a synchronization pattern. This header data is used upon a read back to synchronize to the data written to the storage medium. Based upon the disclosure provided herein, one of ordinary skill in the art will recognize a variety of header data that may be used in relation to different embodiments of the present invention.

One or more of the individual codewords are concatenated to the header data to yield a super sector data set (block 590). Where the amount of data to be written is greater than that which can be stored in a single sector, another header data is generated and remaining portions of the data to be written is concatenated to the next header data to yield another super sector data set. The number of header data and codewords that are assembled into super sector data sets is determined based upon the amount of data that is to be written as part of the received write request.

The prepared super sector data set(s) are written to the selected sector(s) (block 595). This may be done using any write process known in the art. In one particular case, this is done by asserting a write gate at a time corresponding to a user data region of a storage medium at which time a read/write head assembly generates a write field in proximity to the storage medium resulting in magnetic information being stored to the storage medium. Based upon the disclosure provided herein, one of ordinary skill in the art will recognize a variety of approaches that may be used to store data to the storage medium. At the end of each super sector data set, a post-amble pattern is written to the storage medium (block 597). This post-amble pattern is used on a read back to identify the end of the user data.

Alternatively, where the data to be written was previously stored to the storage medium (i.e., this write process is part of a read/modify process) (block 540), the sector(s) where the data was originally written are accessed (block 545) and the data from the sectors is retrieved (block 550). The received data includes super sector data set(s) that are received and divided into individual codewords (block 555). Such division into individual codewords includes synchronizing using a header data and counting the bits received after the end of the header data. A counter is maintained that counts up to the number of bits per codeword. Where a codeword is spread across a sector boundary, the counter continues until the end of the user data region and continues once bits corresponding to the codeword begin being received in the subsequent user data region. As the counter reaches the number of bits per codeword, an indication of a separation between the codewords is asserted, and the next codeword begins to be assembled from the received data. This process continues until all of the codewords from the retrieved data are separated into individual codewords. The individual codewords are provided to a data processing circuit where the codewords are decoded to recover the data originally encoded to make the codewords (block 560). This processing may include, but is not limited to, one or more iterations through a data detector circuit and a data decoder circuit as is known in the art.

The original data is then overwritten to match the write data associated with the write request (block 565). This may include, for example, modifying portions of the data that was read back to match the data provided as part of the write request. One or more of the previously written sectors or one or more new sectors are selected to receive the prepared data set (block 570). Once the sector(s) to be written are selected (block 570), the processes of blocks 580 through 597 discussed above are performed to write the modified data back to the storage medium.

In conclusion, the invention provides novel systems, devices, methods, formats and arrangements for data storage. While detailed descriptions of one or more embodiments of the invention have been given above, various alternatives, modifications, and equivalents will be apparent to those skilled in the art without varying from the spirit of the invention. Therefore, the above description should not be taken as limiting the scope of the invention, which is defined by the appended claims. 

1. A data storage system, the system comprising: a storage medium including a first servo data region and a second servo data region separated by a user data region, wherein the user data region includes a super sector data set including at least a portion of a first low density parity check codeword and a portion of a second low density parity check codeword codeword, and wherein the first low density parity check codeword and the second low density parity check codeword are associated with a common header data.
 2. The data storage system of claim 1, wherein the storage system further comprises: a codeword boundary matching circuit operable to: receive the super sector data set; and divide the super sector data set to yield the first low density parity check codeword and the second low density parity check codeword, wherein the codeword boundary matching circuit includes a counter operable to count the number of bit periods in the super sector data set and to indicate reception of a complete low density parity check codeword.
 3. The data storage system of claim 1, wherein the portion of the first low density parity check codeword is all of the first codeword, and wherein the portion of the second low density parity check codeword is less than all of the second low density parity check codeword.
 4. The data storage system of claim 1, wherein the data storage system further comprises: an encoder circuit operable to: receive write data; encode the write data into the first low density parity check codeword and the second low density parity check codeword; and combine the portion of the first low density parity check codeword with the portion of the second low density parity check codeword and the common header data to form a super sector data set.
 5. The data storage system of claim 4, wherein the encoder circuit further includes a user data region matching circuit, and wherein the user data region matching circuit is operable to combine the portion of the first low density parity check codeword with the portion of the second low density parity check codeword and the common header data into the super sector data set.
 6. The data storage system of claim 4, wherein the super sector data set includes greater than two times the number of bit periods in the first codeword, and less than the number of bit periods of the user data region.
 7. The data storage system of claim 1, wherein the portion of a first low density parity check codeword, the portion of a second low density parity check codeword and the common header data are assembled in a super sector data set, and wherein the data storage system further comprises: a decoder circuit operable to: receive the super sector data set; synchronize to the super sector data set using the common header data; divide the super sector data set to yield the portion of the first low density parity check codeword and the portion of the second low density parity check codeword; and decode the first low density parity check codeword and the second low density parity check codeword to yield an originally written data set.
 8. The data storage system of claim 7, wherein the decoder circuit includes a low density parity check decoder operable to decode the first low density parity check codeword and the second low density parity check codeword.
 9. The data storage system of claim 1, wherein the user data region is a first user data region, wherein the storage medium further includes a third servo data region separated from the second servo data region by a second user data region, wherein the portion of the second low density parity check codeword is a first portion of the second codeword, and wherein a second portion of the second low density parity check codeword is included in the second user data region.
 10. The data storage system of claim 1, wherein the data storage system is implemented as part of a hard disk drive.
 11. The data storage system of claim 1, wherein the data storage system is implemented as part of an integrated circuit.
 12. The data storage system of claim 1, wherein the storage system further comprises: A read/write head assembly disposed in relation to the storage medium.
 13. The data storage system of claim 12, wherein the read/write head assembly is operable to: write the super sector data set to the storage medium; and read the super sector data set from the storage medium.
 14. A method for storing data to a storage medium, the method comprising: receiving a data set; encoding a first portion of the data set into a first low density parity check codeword using a data encoding circuit; encoding a second portion of the data set into a second low density parity check codeword using the data encoding circuit; forming the first low density parity check codeword together with at least a first portion of the second low density parity check codeword to yield a user data portion; writing the user data portion to a storage medium between a first servo data region and a second servo data region.
 15. The method of claim 14, wherein writing the user data portion to a storage medium between a first servo data region and a second servo data region is done using a read/write head assembly disposed in relation to the storage medium.
 16. The method of claim 14, wherein the user data portion is a first user data portion, wherein the portion of the second low density parity check codeword is a first portion of the second low density parity check codeword, and wherein the method further comprises: encoding a third portion of the data set into a third low density parity check codeword using the data encoding circuit; forming the third low density parity check codeword together with at least a second portion of the second low density parity check to yield a second user data portion; writing the second user data portion to the storage medium between the second servo data region and a third servo data region.
 17. The method of claim 16, wherein the method further comprises: reading the first user data portion from the storage medium; dividing the first user data portion to yield the first low density parity check codeword and the first portion of the second low density parity check codeword; reading the second user data portion from the storage medium; dividing the second user data portion to yield the third low density parity check codeword and the second portion of the second low density parity check codeword; and combining the first portion of the second low density parity check codeword with the second portion of the second low density parity check codeword to yield the second low density parity check codeword.
 18. The method of claim 17, wherein: reading the first user data portion from the storage medium includes synchronizing to the first servo data region; and reading the second user data portion from the storage medium includes synchronizing to the second servo data region.
 19. The method of claim 17, wherein the method further comprises: applying a data decode algorithm to the first low density parity check codeword to yield a first decoded output; applying the data decode algorithm to the second low density parity check codeword to yield a second decoded output; and applying the data decode algorithm to the third low density parity check codeword to yield a third decoded output.
 20. The method of claim 19, wherein the method further comprises: assembling the first decoded output, the second decoded output and the third decoded output into a data output. 